Improve FreeType caching again - #182
Merged
Merged
Conversation
Doesn't seem worth it for now. Mostly reverts `a182859d`.
afishhh
force-pushed
the
ft-caching-again
branch
from
June 17, 2026 16:56
e9e65db to
f1fee76
Compare
Owner
Author
|
This is last time I'm touching this file for a bit.. I'm not that happy with it, I'm not happy with what FreeType doesn't let me do, I'm not happy about the fact we even use FreeType for rasterization (but it is twice as fast on small glyphs...), I'm not happy with how caching works (maybe everything should be a binary tree! those always solve all my problems!!), severely lacking happiness right now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the hinting avoidance hack.
Attemps to make bitmap glyphs loaded only once per strike (instead of one per point size).